Distributed ledger platform for improved return logistics

ABSTRACT

Aspects of the disclosure relate to return logistics. A computing platform may process a first request, resulting in first information indicating a first transfer of resources from a buyer of an item to a seller. The computing platform may record, in a distributed ledger, the first information. The computing platform may receive a second request corresponding to another sale of the item, and may process the second request, which may result in second information indicating a second transfer of resources from another buyer to the seller. The computing platform may record, in the distributed ledger, the second information, and may cause the item to be sent from the buyer to the other buyer. The computing platform may identify, using the distributed ledger, that the item has been received by the other buyer, and may cause a third transfer of resources from the seller to the buyer.

BACKGROUND

Aspects of the disclosure relate to supply chain logistics. Inparticular, one or more aspects of the disclosure relate to using adistributed ledger to improve supply chain logistics.

In some instances, re-shelving may create a major bottle neck in supplychain reverse logistics. For example, when an individual returns anitem, it may require time/effort to put the item back into the supplychain so that it may be shipped to another customer. Accordingly, it maybe important to improve the operational efficiency of such supply chainlogistics, in a way that enables computing systems to efficiently andeffectively handle such returns and the corresponding transactions.

SUMMARY

Aspects of the disclosure provide effective, efficient, scalable, andconvenient technical solutions that address and overcome the technicalproblems associated with return logistics. In accordance with one ormore embodiments of the disclosure, a computing platform comprising atleast one processor, a communication interface, and memory storingcomputer-readable instructions may receive a first event processingrequest corresponding to a first sale of an item. The computing platformmay process the first event processing request, resulting in first eventprocessing information indicating a first transfer of resources from afirst buyer of the item to a seller of the item. The computing platformmay create a first element of a distributed ledger corresponding to theitem. The computing platform may record, in the first element of thedistributed ledger corresponding to the item, the first event processinginformation, an identity of the first buyer, and an identity of theseller, and a first portion of distributed ledger may be visible to thefirst buyer and the seller. The computing platform may receive a secondevent processing request corresponding to a second sale of the item. Thecomputing platform may process the second event processing request,which may result in second event processing information indicating asecond transfer of resources from a second buyer of the item to theseller. The computing platform may create a second element of thedistributed ledger. The computing platform may record, in the secondelement of the distributed ledger, the second event processinginformation, a return policy for the item, an identity of the secondbuyer, and the identity of the seller, where the second portion of thedistributed ledger may be visible to the second buyer and the seller.The computing platform may cause the item to be sent from the firstbuyer to the second buyer, where the first buyer may have sent a requestto return the item, and where causing the item to be sent from the firstbuyer to the second buyer may include: 1) generating, based on thedistributed ledger, anonymous shipping information corresponding to thesecond buyer, 2) allowing the first buyer to access the anonymousshipping information using the distributed ledger, 3) recording shippingconfirmation information indicating that the item has been shipped fromthe first buyer to the second buyer, and 4) recording receiptconfirmation information indicating that the item has been received bythe second buyer. The computing platform may identify, using thedistributed ledger, that the item has been received by the second buyer.Based on identifying that the item has been received by the secondbuyer, the computing platform may process a third event, which may causea third transfer of resources, equal to the first transfer of resources,from the seller to the first buyer.

In one or more instances, generating the anonymous shipping informationmay be based on analyzing the return policy. In one or more instances,the anonymous shipping information may be a quick response (QR) code.

In one or more embodiments, the anonymous shipping information may be alabel that may be used by a shipping company to send the item to thesecond buyer, and that does not expose, to the first buyer, an identityof the second buyer. In one or more instances, the distributed ledgermay be a blockchain.

In one or more instances, the first transfer of resources may bedifferent than the second transfer of resources. In one or moreinstances, the computing platform may generate one or more commandsdirecting a user device of the first buyer to display a graphical userinterface indicating that the return has been completed. The computingplatform may send, to the user device, the one or more commands todisplay the graphical user interface indicating that the return has beencompleted, which may cause the user device to display the graphical userinterface indicating that the return has been completed.

In one or more embodiments, the first transfer of resources may be afund transfer from an account of the first buyer to an account of theseller. The second transfer of resources may include a fund transferfrom an account of the second buyer to the account of the seller. Thethird transfer of resources may include a fund transfer from the accountof the seller to the account of the first buyer.

In one or more instances, the first buyer may be unable to access: 1)the identity of the second buyer using the distributed ledger, and 2) anamount paid by the second buyer for the item. In one or more instances,the computing platform may generate, using the distributed ledger, oneor more smart contracts corresponding to sales of the item, where theone or more smart contracts may be used by an entity corresponding tothe computing platform to identify when resources should be returnedfrom the seller to the first buyer.

These features, along with many others, are discussed in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and not limitedin the accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIGS. 1A-1B depict an illustrative computing environment for improvedreturn logistics using a distributed ledger in accordance with one ormore example embodiments;

FIGS. 2A-2F depict an illustrative event sequence for improved returnlogistics using a distributed ledger in accordance with one or moreexample embodiments;

FIG. 3 depicts an illustrative method for improved return logisticsusing a distributed ledger in accordance with one or more exampleembodiments; and

FIG. 4 depicts an illustrative graphical user interface for improvedreturn logistics using a distributed ledger in accordance with one ormore example embodiments.

DETAILED DESCRIPTION

In the following description of various illustrative embodiments,reference is made to the accompanying drawings, which form a parthereof, and in which is shown, by way of illustration, variousembodiments in which aspects of the disclosure may be practiced. In someinstances, other embodiments may be utilized, and structural andfunctional modifications may be made, without departing from the scopeof the present disclosure.

It is noted that various connections between elements are discussed inthe following description. It is noted that these connections aregeneral and, unless specified otherwise, may be direct or indirect,wired or wireless, and that the specification is not intended to belimiting in this respect.

As a brief introduction to the concepts described further herein, one ormore aspects of the disclosure describe systems and methods for improvedreturn logistics. For example, in the reverse logistics of a supplychain, re-shelving may be a major bottle neck that may be difficult tosolve. Even for an item that may be returned in perfect factorycondition without any damage or missing parts, it may take significanteffort to put the item back into the supply chain so that it may beshipped back to another customer.

In order to solve for this problem of re-shelving or re-warehousingitems (e.g., restocking items that have been returned to a seller by abuyer), many retailers or wholesalers may consider asking customers toreturn the items to another customer who might have a need for the item(for instance, instead of returning the item to the seller). In thisway, the item may stay within the forward path of the supply chain, andmight not fall into reverse logistics.

For example, customer X may need an item urgently, and may order it frommultiple vendors (vendor A and vendor B). Once the item from vendor Aarrives, customer X may decide that they have enough of the particularitem already, and may want to return the item from vendor B. Undernormal circumstances, the item returned to vendor B may stay on a shelffor a long time, along with other items that may or might not bereturned to the supply chain later. However, if instead vendor B directscustomer X to send the item to customer Y who might have a need for theitem, it may solve the problem of re-shelving, as well as the problem ofurgently needing the item to be delivered in time. This is one exampleof the item staying within the forward path of the supply chain and notfalling into the reverse logistics.

However, it may be difficult to handle the transactions of several bankaccounts for credits and debits using the approach described above. Forexample, vendor B should not only credit the account of customer X—itshould also debit the account of customer Y. The problem may get morecomplicated when the transactions are handled by one large corporationproviding the supply chain facilities to different market participantvendors and customers.

Accordingly, described herein is a solution to these problems. In someinstances, the blockchain described herein may be provided by afinancial institution to a supply chain organization for all customersand vendors.

A blockchain is a growing list of records, called blocks, which may belinked using cryptography. Each block may contain a cryptographic hashof the previous block, a timestamp, and transaction data (which may berepresented as a Merkle tree). By design, a blockchain may be immutableor resistant to modification of its data. This is because once recorded,the data in any given block cannot be altered retroactively withoutalteration of all subsequent blocks.

For use as a distributed ledger, a blockchain may be managed by a peerto peer network collectively adhering to a protocol for inter-nodecommunication and validating new blocks. Although blockchain records arenot unalterable, blockchain may be considered secure by design andexemplify a distributed computing system with high Byzantine faulttolerance. The blockchain has been described as an open distributedledger that may record transactions between two parties efficiently andin a verifiable and permanent way.

Blockchain has not previously been used where more than two parties areinvolved in the return of an item and reverse logistics are turned intoforward logistics. However, because blockchain is an immutable openledger, it may provide the basic trustless mechanism to handletransactions that involve more than two parties.

Simply put, whenever a transaction occurs during the life cycle of aproduct, the transaction is recorded on the blockchain, which may beverified by each party. For example, the following items (as describedabove) may be recorded in a blockchain as a set of transactions: 1)customer X makes a request to return an item to vendor B, 2) customer Ymakes a request to purchase the same item from vendor B, 3) vendor Bdetermines that: a) customer Y has made a request to purchase the sameitem that customer X wants to return, b) vendor B approves the requestand sends a return receipt for customer X addressed to customer Y, c)customer X ships the item to customer Y, and it may be recorded on theblockchain by vendor B by the notification from the shipping company,and d) customer Y receives and acknowledges the receipt of the item, and4) vendor B credits the account of customer X and debits the account ofcustomer Y.

Since the entire transaction is on the open ledger, it may be verifiedby all interested parties and stake holders such as customers X and Y,vendor B, the shipping company, and/or other parties. The wholeblockchain may be provided by a financial institution to anothercompany, such as a company that hosts an online market for multiplecustomers/vendors. This type of multi-party reverse logistics system maybe implemented on a blockchain either for a cryptocurrency, a regularcurrency, and/or a mixture of any currency types.

FIGS. 1A-1B depict an illustrative computing environment for improvedreturn logistics using a distributed ledger in accordance with one ormore example embodiments. Referring to FIG. 1A, computing environment100 may include one or more computer systems. For example, computingenvironment 100 may include distributed ledger host platform 102, vendorcomputing system 103, first user computing device 104, and second usercomputing device 105.

As described further below, distributed ledger host platform 102 may bea computer system that includes one or more computing devices (e.g.,servers, server blades, or the like) and/or other computer components(e.g., processors, memories, communication interfaces) that may beconfigured to establish, host, and otherwise maintain a distributedledger (e.g., a blockchain). In some instances, the distributed ledgerhost platform 102 may be managed by, affiliated with, or otherwisecorrespond to a financial institution, and may be configured to host thedistributed ledger on behalf of a market (e.g., live or online) thatserves as a selling/purchasing platform for multiple vendors/purchasers.For example, the distributed ledger host platform 102 may be configuredto maintain, using the distributed ledger, records of transactionsbetween various buyers and sellers, and to use the distributed ledger toexecute one or more events (e.g., a fund transfer).

Vendor computing system 103 may be a computer system that includes oneor more computing devices (e.g., desktop computers, laptop computers,mobile devices, smartphones, tablets, servers, server blades, or thelike) and/or other computer components (e.g., processors, memories,communication interfaces) that may be configured to host the marketdescribed above, and to facilitate transactions between various buyersand sellers. Additionally or alternatively, the vendor computing system103 may be affiliated with a particular vendor or merchant, and may beconfigured to manage sales, returns, and/or other transactions for thatvendor.

First user computing device 104 may be a laptop computer, desktopcomputer, mobile device, tablet, smartphone, or the like that may beused by a customer to conduct one or more transactions with the vendorcomputing system 103 (e.g., purchases, returns, and/or othertransactions). In some instances, first user computing device 104 may beconfigured to display one or more user interfaces (e.g., purchasinginterfaces, return interfaces, and/or other interfaces).

Second user computing device 105 may be a laptop computer, desktopcomputer, mobile device, tablet, smartphone, or the like that may beused by a customer (e.g., a different customer) to conduct one or moretransactions with the vendor computing system 103 (e.g., purchases,returns, and/or other transactions). In some instances, second usercomputing device 105 may be configured to display one or more userinterfaces (e.g., purchasing interfaces, return interfaces, and/or otherinterfaces).

Computing environment 100 also may include one or more networks, whichmay interconnect distributed ledger host platform 102, vendor computingsystem 103, first user computing device 104, and/or second usercomputing device 105. For example, computing environment 100 may includea network 101 (which may interconnect, e.g., distributed ledger hostplatform 102, vendor computing system 103, first user computing device104, and/or second user computing device 105).

In one or more arrangements, distributed ledger host platform 102,vendor computing system 103, first user computing device 104, and/orsecond user computing device 105 may be any type of computing devicecapable of sending and/or receiving requests and processing the requestsaccordingly. For example, distributed ledger host platform 102, vendorcomputing system 103, first user computing device 104, second usercomputing device 105 and/or the other systems included in computingenvironment 100 may, in some instances, be and/or include servercomputers, desktop computers, laptop computers, tablet computers, smartphones, or the like that may include one or more processors, memories,communication interfaces, storage devices, and/or other components. Asnoted above, and as illustrated in greater detail below, any and/or allof distributed ledger host platform 102, vendor computing system 103,first user computing device 104, and/or second user computing device105, may, in some instances, be special-purpose computing devicesconfigured to perform specific functions.

Referring to FIG. 1B, distributed ledger host platform 102 may includeone or more processors 111, memory 112, and communication interface 113.A data bus may interconnect processor 111, memory 112, and communicationinterface 113. Communication interface 113 may be a network interfaceconfigured to support communication between distributed ledger hostplatform 102 and one or more networks (e.g., network 101, or the like).Memory 112 may include one or more program modules having instructionsthat when executed by processor 111 cause distributed ledger hostplatform 102 to perform one or more functions described herein and/orone or more databases that may store and/or otherwise maintaininformation which may be used by such program modules and/or processor111. In some instances, the one or more program modules and/or databasesmay be stored by and/or maintained in different memory units ofdistributed ledger host platform 102 and/or by different computingdevices that may form and/or otherwise make up distributed ledger hostplatform 102. For example, memory 112 may have, host, store, and/orinclude distributed ledger host module 112 a, distributed ledger hostdatabase 112 b, and machine learning engine 112 c.

Distributed ledger host module 112 a may have instructions that directand/or cause distributed ledger host platform 102 to execute advancedreturn logistics procedures. Distributed ledger host database 112 b maystore information used by distributed ledger host module 112 a and/ordistributed ledger host platform 102 in application of advanced returnlogistics procedures, and/or in performing other functions. Machinelearning engine 112 c may have instructions that direct and/or cause thedistributed ledger host platform 102 to set, define, and/or iterativelyrefine optimization rules and/or other parameters used by thedistributed ledger host platform 102 and/or other systems in computingenvironment 100.

FIGS. 2A-2F depict an illustrative event sequence for improved returnlogistics using a distributed ledger in accordance with one or moreexample embodiments. Referring to FIG. 2A, at step 201, first usercomputing device 104 may establish a connection with the vendorcomputing system 103. For example, the first user computing device 104may establish a first wireless data connection with the vendor computingsystem 103 to link the first user computing device 104 to the vendorcomputing system 103 (e.g., in preparation for sending a first purchaserequest). In some instances, the first user computing device 104 mayidentify whether or not a connection is already established with thevendor computing system 103. If a connection is already established, thefirst user computing device 104 might not re-establish the connection.If a connection is not yet established, the first user computing device104 may establish the first wireless data connection as describedherein.

At step 202, the first user computing device 104 may send a firstpurchase request to the vendor computing system 103. For example, thefirst user computing device 104 may send a first purchase request to thevendor computing system 103, requesting that an item be purchased for auser of the first user computing device 104 (e.g., a first buyer) froman enterprise associated with the vendor computing system 103 (e.g., aseller). In some instances, the first user computing device 104 may sendthe first purchase request to the vendor computing system 103 while thefirst wireless data connection is established. In some instances, insending the first purchase request, the first user computing device 104may send an identifier of the item to be purchased and paymentinformation (e.g., account number, credit card number, and/or otherpayment information) that may be used to process the sale.

At step 203, the vendor computing system 103 may receive the firstpurchase request (e.g., the seller may receive the order for the item).For example, the vendor computing system 103 may receive the firstpurchase request from the first user computing device 104 while thefirst wireless data connection is established.

At step 204, the vendor computing system 103 may establish a connectionwith the distributed ledger host platform 102. For example, the vendorcomputing system 103 may establish a second wireless data connectionwith the distributed ledger host platform 102 to link the vendorcomputing system 103 to the distributed ledger host platform 102 (e.g.,in preparation for sending an event processing request). In someinstances, the vendor computing system 103 may identify whether or not aconnection is already established with the distributed ledger hostplatform 102. If a connection is already established with thedistributed ledger host platform 102, the vendor computing system 103might not re-establish the connection. If a connection is not yetestablished with the distributed ledger host platform 102, the vendorcomputing system 103 may establish the second wireless data connectionas described herein.

At step 205, the vendor computing system 103 may send a first eventprocessing request (e.g., a request to transfer resources/funds from thefirst buyer to the seller) to the distributed ledger host platform 102.For example, the vendor computing system 103 may send the paymentinformation that may be processed in exchange for the item. In someinstances, the vendor computing system 103 may also send informationidentifying the first user, the item, and/or other information relatedto the sale. In some instances, the vendor computing system 103 may sendthe first event processing request to the distributed ledger hostplatform 102 while the second wireless data connection is established.

At step 206, the distributed ledger host platform 102 may receive thefirst event processing request sent at step 205. For example, thedistributed ledger host platform 102 may receive the first eventprocessing request via the communication interface 113 and while thesecond wireless data connection is established.

Referring to FIG. 2B, at step 207, the distributed ledger host platform102 may process the first event. For example, the distributed ledgerhost platform 102 may be controlled or otherwise affiliated with afinancial institution, and may cause funds (equal to the sale price ofthe item) to be transferred from the first buyer (e.g., from a bankaccount or other source of funds) to the seller (e.g., into an accountor the like).

At step 208, the distributed ledger host platform 102 may record firstevent processing information in a distributed ledger hosted by thedistributed ledger host platform 102. For example, the distributedledger host platform 102 may create a first block in a blockchaincorresponding to the sale of the item between the first buyer and theseller. In some instances, the distributed ledger host platform 102 mayrecord information such as time, date, first buyer identity, sale price,seller identity, and/or other information in the first block. In someinstances, the first block of the blockchain may be accessible to theseller, the first buyer, employees of the financial institution, but mayotherwise not be accessible by other individuals (the blockchain may bea private blockchain). In some instances, the distributed ledger hostplatform 102 may configure information stored in the first block of theblockchain to be selectively concealed to certain parties who mayotherwise have access to the full first block. In some instances, ratherthan sending information to the distributed ledger host platform 102,and having the distributed ledger host platform 102 write theinformation to the block, the vendor computing system and/or first usercomputing device 104 may directly write/record the information in thefirst block. In some instances, in recording the first event processinginformation, the distributed ledger host platform 102 may generate asmart contract corresponding to the sale of the item, and which maysubsequently be used to identify when resources should be transferredfrom the seller to the first buyer in the event of a return.

At step 209, the vendor computing system 103 may access the distributedledger (e.g., the first block established at step 208) to confirm thatthe first event was processed (e.g., that the first buyer successfullypaid for the item). If the vendor computing system 103 identifies thatthe first event was not successfully processed, a notification may besent to the first user computing device 104, and the first usercomputing device 104 may return to step 202 to resubmit the firstpurchase request, or otherwise modify the transaction. If the vendorcomputing system 103 identifies that the first event was successfullyprocessed, the distributed ledger host platform 102 may proceed to step209.

At step 210, the vendor computing system 103 may cause the first item tobe shipped to the first buyer. For example, the vendor computing system103 may display an interface directing one or more individuals toinitiate a shipping process and/or may communicate directly with acomputing system corresponding to a shipping company, indicating thatthe item should be shipped to the first buyer.

Referring to FIG. 2C, at step 211, the vendor computing system 103 mayrecord first shipping confirmation information in the first block of thedistributed ledger. For example, the vendor computing system 103 maydirectly access the first block, or may otherwise communicate with thedistributed ledger host platform 102 to cause the distributed ledgerhost platform 102 to write/record the first shipping confirmationinformation in the first block. For example, in recording the firstshipping confirmation information, the vendor computing system 103 mayrecord information indicating that the item was successfully shipped toand/or received by the first buyer.

At step 212, the first user computing device 104 may send a returnrequest to the vendor computing system 103. For example, the first usercomputing device 104 may send a message to the vendor computing system103 notifying the vendor computing system 103 that the item will bereturned. In some instances, the first user computing device 104 maysend the return request to the vendor computing system 103 while thefirst wireless data connection is established.

At step 213, the vendor computing system 103 may receive the returnrequest sent at step 212. For example, the vendor computing system 103may receive the return request while the first wireless data connectionis established.

At step 214, the second user computing device 105 may establish aconnection with the vendor computing system 103. For example, the seconduser computing device 105 may establish a third wireless data connectionwith the vendor computing system 103 to link the second user computingdevice 105 to the vendor computing system 103 (e.g., for purposes ofsending a second purchase request). In some instances, the second usercomputing device 105 may identify whether or not a connection is alreadyestablished with the vendor computing system 103. If a connection isalready established with the vendor computing system 103, the seconduser computing device 105 might not re-establish the connection. If aconnection is not yet established with the vendor computing system 103,the second user computing device 105 may establish the third wirelessdata connection as described herein.

At step 215, the user computing device 105 may send a second purchaserequest to the vendor computing system 103. For example, the usercomputing device 105 may send the second purchase request to the vendorcomputing system 103 while the third wireless data connection isestablished. Actions performed at step 215 by the second user computingdevice 105 may be similar to those described at step 202 with regard tothe first user computing device 104.

At step 216, the vendor computing system 103 may receive the secondpurchase request. For example, the vendor computing system 103 mayreceive the second purchase request while the third wireless dataconnection is established. Actions performed at step 216 may be similarto those described above at step 204 with regard to the first purchaserequest.

Referring to FIG. 2D, at step 217, the vendor computing system 103 maysend the second event processing request (e.g., requesting a transfer offunds/resources from an account of the second buyer to an account of theseller) to the distributed ledger host platform 102. For example, thevendor computing system 103 may send the second event processing requestto the distributed ledger host platform 102 while the second wirelessdata connection is established. In some instances, actions performed atstep 217 may be similar to those described at step 205 with regard tothe first event processing request. In some instances, the second eventprocessing request may be a request to process a different quantity ofresources/funds than the first event processing request (e.g., a priceof the item may have fluctuated up or down since the first buyerpurchased the item).

At step 218, the distributed ledger host platform 102 may receive thesecond event processing request. For example, the distributed ledgerhost platform 102 may receive the second event processing request whilethe second wireless data connection is established. In some instances,actions performed at step 218 may be similar to those described above atstep 206 with regard to the first event processing request.

At step 219, the distributed ledger host platform 102 may process thesecond event (e.g., cause a transfer of funds from the second buyer tothe seller). For example, actions performed at step 219 may be similarto those described above at step 207 with regard to the first event.

At step 220, the distributed ledger host platform 102 may record secondevent processing information, indicating that the second event wassuccessfully processed (e.g., that funds were successfully transferred).In some instances, the distributed ledger host platform 102 may computea hash of the first block, and, using the hash of the first block, maygenerate a second block in the distributed ledger. After generating thissecond block, the distributed ledger host platform 102 may record thesecond event processing information in the second block. In someinstances, the distributed ledger host platform 102 may recordinformation such as time, date, second buyer identity, sale price,seller identity, and/or other information in the second block. In someinstances, the first block of the blockchain may be accessible to theseller, the second buyer, and employees of the financial institution,but may otherwise not be accessible by other individuals (the blockchainmay be a private blockchain). In some instances, the distributed ledgerhost platform 102 may configure information stored in the second blockof the blockchain to be selectively concealed to certain parties who mayotherwise have access to the full second block. For example, the seconduser computing device 105 may be unable to access a sale price betweenthe first buyer and the seller (e.g., because the first buyer may, insome instances, have paid a lower price than the second buyer for thesame item), an identity of the seller, and/or other information. In someinstances, rather than sending information to the distributed ledgerhost platform 102, and having the distributed ledger host platform 102write the information to the block, the vendor computing system and/orsecond user computing device 105 may directly write/record theinformation in the second block. In some instances, actions performed atstep 220 may be similar to those performed at step 208 with regard tothe first event processing information.

In some instances, in recording the second event processing information,the distributed ledger host platform 102 may generate a smart contractcorresponding to the sale of the item, and which may subsequently beused to identify when resources should be transferred from the seller tothe first buyer in the event of a return.

In some instances, after receiving the return request from the firstbuyer and the purchase request from the second buyer, the distributedledger host platform 102 may embed a return policy into the secondblock, which may indicate anonymous shipping information for the secondbuyer (e.g., a QR code, non-identifying shipping label, and/or otherinformation that may be used to ship the item from the first buyer tothe second buyer). In some instances, the first buyer may be able toaccess the return policy in the second block, but might not be able toaccess other information in the second block, such as an identifier ofthe second buyer, a purchase price, and/or other information.

At step 221, the vendor computing system 103 may access the distributedledger (e.g., the second block established at step 220) to confirm thatthe second event was processed (e.g., that the second buyer successfullypaid for the item). If the vendor computing system 103 identifies thatthe second event was not successfully processed, a notification may besent to the second user computing device 105, and the second usercomputing device 105 may return to step 212 to resubmit the secondpurchase request, or otherwise modify the transaction. If the vendorcomputing system 103 identifies that the second event was successfullyprocessed, the distributed ledger host platform 102 may proceed to step222.

Referring to FIG. 2E, at step 222, the first user computing device 104may identify a return policy by accessing the distributed ledger. Forexample, the first user computing device 104 may communicate with thedistributed ledger host platform 102 to access the return policy in thesecond block. In doing so, the first user computing device 104 mayaccess a quick response (QR) code and/or other anonymous shippinginformation (e.g., a shipping label that may be used by a shippingcompany to send the item to the second buyer, and that does not expose,to the first buyer, an identity of the second buyer) that may enable thefirst buyer to ship the item to the second buyer (e.g., without firstbeing returned to the seller) without knowing the identity of the secondbuyer.

At step 223, the first user computing device 104 may record shippingconfirmation information (indicating that the first buyer shipped theitem to the second buyer) in the second block of the distributed ledger.For example, the first user computing device 104 may directly access thedistributed ledger to record the shipping confirmation information, ormay send the shipping confirmation information to the distributed ledgerhost platform 102, which may cause the distributed ledger host platform102 to record the shipping confirmation information.

At step 224, the second user computing device 105 may record shippingacknowledgement information (indicating that the second buyer receivedthe item from the first buyer) in the second block of the distributedledger. For example, the second user computing device 105 may directlyaccess the distributed ledger to record the shipping confirmationinformation, or may send the shipping acknowledgement information to thedistributed ledger host platform 102, which may cause the distributedledger host platform 102 to record the shipping acknowledgementinformation.

At step 225, the distributed ledger host platform 102 may identify, byanalyzing the distributed ledger, that the second buyer has successfullyreceived the item from the first buyer. Accordingly, the distributedledger host platform 102 may determine that the first buyer may berefunded, and may process a third event (corresponding to a fundtransfer from an account of the seller, to an account of the firstbuyer). In some instances, the distributed ledger host platform 102 mayconsult one or more of the generated smart contracts to confirm thatresources may be returned to the first buyer from the seller at thistime. In some instances, the distributed ledger host platform 102 mayrecord third event processing information (indicating that the thirdevent was successfully processed) in the distributed ledger (e.g., inthe second block). In some instances, rather than waiting merely untilthe second buyer has successfully received the item from the firstbuyer, the distributed ledger host platform 102 may process the thirdevent in response to identifying that the second buyer has acknowledgedreceipt of the item. In some instances, this information may be embeddedin the return policy.

Referring to FIG. 2F, at step 226, the distributed ledger host platform102 may send one or more commands directing the first user computingdevice 104 to display a refund interface (e.g., indicating that thepurchase of the item by the first buyer was successfully refunded). Insome instances, the distributed ledger host platform 102 may send theone or more commands via the communication interface 113 and while awireless data connection is established with the first user computingdevice 104 (e.g., a fourth wireless data connection).

At step 227, the first user computing device 104 may receive the one ormore commands directing the first user computing device 104 to displaythe refund interface. For example, the first user computing device 104may receive the one or more commands while the fourth wireless dataconnection is established.

At step 228, based on or in response to the one or more commandsdirecting the first user computing device 104 to display the refundinterface, the first user computing device 104 may display the refundinterface. For example, the first user computing device 104 may displaya graphical user interface similar to graphical user interface 405,which is shown in FIG. 4 .

In some instances, the above described event sequence may involve theexchange of cryptocurrency, regular currency, or any combinationthereof.

Accordingly, by applying the methods described herein, transactionsbetween multiple parties may be efficiently executed/recorded in averifiable and permanent way (e.g., because data in previous blocksmight not be altered retroactively without alteration of all subsequentblocks), and thus transactions may be efficiently processed incircumstances where an initial buyer of an item returns the item byshipping it to a subsequent buyer, rather than returning the item to amerchant. Although a single merchant and two buyers are describedherein, any number of merchants/buyers may be involved without departingfrom the scope of the disclosure herein.

FIG. 3 depicts an illustrative method for improved return logisticsusing a distributed ledger in accordance with one or more exampleembodiments. Referring to FIG. 3 , at step 305, a computing platformhaving at least one processor, a communication interface, and memory mayreceive a first event processing request. At step 310, the computingplatform may process the first event. At step 315, the computingplatform may record the first event in a distributed ledger. At step320, the computing platform may enable a first user device to access thedistributed ledger. At step 325, the computing platform may recordshipping confirmation information in the distributed ledger. At step330, the computing platform may identify whether a second eventprocessing request was received. If a second event processing requestwas not received, the computing platform may return to step 305. If asecond event processing request was received, the computing platform mayproceed to step 335.

At step 335, the computing platform may process the second event. Atstep 340, the computing platform may record the second event in thedistributed ledger. At step 345, the computing platform may enabledistributed ledger access to a merchant computing device. At step 350,the computing platform may further enable the first user computingdevice to access the distributed ledger. At step 355, the computingplatform may enable the second user computing device to access thedistributed ledger. At step 360, the computing platform may identifywhether or not receipt of a shipped item was received. If not, thecomputing platform may return to step 350. If so, the computing platformmay proceed to step 365.

At step 365, the computing platform may process a third event. At step370, the computing platform may send one or more commands directing thefirst user computing device to display a refund interface.

One or more aspects of the disclosure may be embodied in computer-usabledata or computer-executable instructions, such as in one or more programmodules, executed by one or more computers or other devices to performthe operations described herein. Generally, program modules includeroutines, programs, objects, components, data structures, and the likethat perform particular tasks or implement particular abstract datatypes when executed by one or more processors in a computer or otherdata processing device. The computer-executable instructions may bestored as computer-readable instructions on a computer-readable mediumsuch as a hard disk, optical disk, removable storage media, solid-statememory, RAM, and the like. The functionality of the program modules maybe combined or distributed as desired in various embodiments. Inaddition, the functionality may be embodied in whole or in part infirmware or hardware equivalents, such as integrated circuits,application-specific integrated circuits (ASICs), field programmablegate arrays (FPGA), and the like. Particular data structures may be usedto more effectively implement one or more aspects of the disclosure, andsuch data structures are contemplated to be within the scope of computerexecutable instructions and computer-usable data described herein.

Various aspects described herein may be embodied as a method, anapparatus, or as one or more computer-readable media storingcomputer-executable instructions. Accordingly, those aspects may takethe form of an entirely hardware embodiment, an entirely softwareembodiment, an entirely firmware embodiment, or an embodiment combiningsoftware, hardware, and firmware aspects in any combination. Inaddition, various signals representing data or events as describedherein may be transferred between a source and a destination in the formof light or electromagnetic waves traveling through signal-conductingmedia such as metal wires, optical fibers, or wireless transmissionmedia (e.g., air or space). In general, the one or morecomputer-readable media may be and/or include one or more non-transitorycomputer-readable media.

As described herein, the various methods and acts may be operativeacross one or more computing servers and one or more networks. Thefunctionality may be distributed in any manner, or may be located in asingle computing device (e.g., a server, a client computer, and thelike). For example, in alternative embodiments, one or more of thecomputing platforms discussed above may be combined into a singlecomputing platform, and the various functions of each computing platformmay be performed by the single computing platform. In such arrangements,any and/or all of the above-discussed communications between computingplatforms may correspond to data being accessed, moved, modified,updated, and/or otherwise used by the single computing platform.Additionally or alternatively, one or more of the computing platformsdiscussed above may be implemented in one or more virtual machines thatare provided by one or more physical computing devices. In sucharrangements, the various functions of each computing platform may beperformed by the one or more virtual machines, and any and/or all of theabove-discussed communications between computing platforms maycorrespond to data being accessed, moved, modified, updated, and/orotherwise used by the one or more virtual machines.

Aspects of the disclosure have been described in terms of illustrativeembodiments thereof. Numerous other embodiments, modifications, andvariations within the scope and spirit of the appended claims will occurto persons of ordinary skill in the art from a review of thisdisclosure. For example, one or more of the steps depicted in theillustrative figures may be performed in other than the recited order,and one or more depicted steps may be optional in accordance withaspects of the disclosure.

What is claimed is:
 1. A computing platform for performing a blockchainand smart contract based method to reduce delivery time and preventreverse supply chain logistics for events corresponding to multipleaccounts while maintaining party anonymity, the computing platformcomprising: at least one processor; a communication interfacecommunicatively coupled to the at least one processor; and memorystoring computer-readable instructions that, when executed by the atleast one processor, cause the computing platform to: receive a firstevent processing request corresponding to a first sale of an item;process the first event processing request, resulting in first eventprocessing information indicating a first transfer of resources from afirst buyer of the item to a seller of the item; create a first elementof a distributed ledger corresponding to the item; record, in the firstelement of the distributed ledger corresponding to the item, the firstevent processing information, an identity of the first buyer, and anidentity of the seller, wherein a first portion of distributed ledger isvisible to the first buyer and the seller, and wherein recording thefirst event processing information further comprises generating a smartcontract indicating when resources are to be transferred from the sellerto the first buyer in case of a return; cause, by communicating with ashipping computing system, the item to be shipped to the first buyer;receive a second event processing request corresponding to a second saleof the item; process the second event processing request, resulting insecond event processing information indicating a second transfer ofresources from a second buyer of the item to the seller, and wherein useof the distributer ledger ensures security of the first event processingrequest and the second event processing request; create a second elementof the distributed ledger corresponding to the item; record, in thesecond element of the distributed ledger, the second event processinginformation, an identity of the second buyer, a return policy for theitem, and the identity of the seller, wherein a second portion of thedistributed ledger is visible to the second buyer and the seller; causethe item to be sent from the first buyer to the second buyer, whereinthe first buyer sent a request to return the item, and wherein causingthe item to be sent from the first buyer to the second buyer comprises:generating, based on the distributed ledger, anonymous shippinginformation corresponding to the second buyer, wherein the anonymousshipping information comprises a quick response (QR) code, allowing thefirst buyer to access the anonymous shipping information using thedistributed ledger, recording shipping confirmation informationindicating that the item has been shipped from the first buyer to thesecond buyer, wherein causing the item to be sent from the first buyerto the second buyer reduces a delivery time associated with shipping theitem to the second buyer and prevents the reverse supply chainlogistics, and recording receipt confirmation information indicatingthat the item has been received by the second buyer; identify, using thedistributed ledger, that the item has been received by the second buyer;and based on identifying that the item has been received by the secondbuyer and identifying that conditions of the smart contract have beensatisfied, process a third event, wherein processing the third eventcomprises causes a third transfer of resources, equal to the firsttransfer of resources, from the seller to the first buyer.
 2. Thecomputing platform of claim 1, wherein generating the anonymous shippinginformation is based on analyzing the return policy.
 3. The computingplatform of claim 1, wherein the anonymous shipping information furthercomprises a label that may be used by a shipping company to send theitem to the second buyer, and that does not expose, to the first buyer,an identity of the second buyer.
 4. The computing platform of claim 1,wherein the distributed ledger comprises a blockchain.
 5. The computingplatform of claim 1, wherein the first transfer of resources isdifferent than the second transfer of resources.
 6. The computingplatform of claim 1, wherein the memory stores additionalcomputer-readable instructions that, when executed by the at least oneprocessor, cause the computing platform to: generate one or morecommands directing a user device of the first buyer to display agraphical user interface indicating that the return has been completed;send, to the user device, the one or more commands to display thegraphical user interface indicating that the return has been completed,wherein sending the one or more commands to display the graphical userinterface indicating that the return has been completed causes the userdevice to display the graphical user interface indicating that thereturn has been completed.
 7. The computing platform of claim 1,wherein: the first transfer of resources comprises a fund transfer froman account of the first buyer to an account of the seller; the secondtransfer of resources comprises a fund transfer from an account of thesecond buyer to the account of the seller; and the third transfer ofresources comprises a fund transfer from the account of the seller tothe account of the first buyer.
 8. The computing platform of claim 1,wherein the first buyer is unable to access: the identity of the secondbuyer using the distributed ledger, and an amount paid by the secondbuyer for the item.
 9. A method for performing a blockchain and smartcontract based method to reduce delivery time and prevent reverse supplychain logistics for events corresponding to multiple accounts whilemaintaining party anonymity, the method comprising: receiving a firstevent processing request corresponding to a first sale of an item;processing the first event processing request, resulting in first eventprocessing information indicating a first transfer of resources from afirst buyer of the item to a seller of the item; creating a firstelement of a distributed ledger corresponding to the item; recording, inthe first element of the distributed ledger corresponding to the item,the first event processing information, an identity of the first buyer,and an identity of the seller, wherein a first portion of distributedledger is visible to the first buyer and the seller, and whereinrecording the first event processing information further comprisesgenerating a smart contract indicating when resources are to betransferred from the seller to the first buyer in case of a return;causing, by communicating with a shipping computing system, the item tobe shipped to the first buyer; receiving a second event processingrequest corresponding to a second sale of the item; processing thesecond event processing request, resulting in second event processinginformation indicating a second transfer of resources from a secondbuyer of the item to the seller; creating a second element of thedistributed ledger corresponding to the item; recording, in the secondelement of the distributed ledger, the second event processinginformation, an identity of the second buyer, a return policy for theitem, and the identity of the seller, wherein a second portion of thedistributed ledger is visible to the second buyer and the seller, andwherein use of the distributer ledger ensures security of the firstevent processing request and the second event processing request;causing the item to be sent from the first buyer to the second buyer,wherein the first buyer sent a request to return the item, and whereincausing the item to be sent from the first buyer to the second buyercomprises: generating, based on the distributed ledger, anonymousshipping information corresponding to the second buyer, wherein theanonymous shipping information comprises a quick response (QR) code,allowing the first buyer to access the anonymous shipping informationusing the distributed ledger, recording shipping confirmationinformation indicating that the item has been shipped from the firstbuyer to the second buyer, and recording receipt confirmationinformation indicating that the item has been received by the secondbuyer, wherein causing the item to be sent from the first buyer to thesecond buyer reduces a delivery time associated with shipping the itemto the second buyer and prevents the reverse supply chain logistics;identify, using the distributed ledger, that the item has been receivedby the second buyer; and based on identifying that the item has beenreceived by the second buyer and identifying that conditions of thesmart contract have been satisfied, processing a third event, whereinprocessing the third event comprises causes a third transfer ofresources, equal to the first transfer of resources, from the seller tothe first buyer.
 10. The method of claim 9, wherein generating theanonymous shipping information is based on analyzing the return policy.11. The method of claim 9, wherein the anonymous shipping informationfurther comprises a label that may be used by a shipping company to sendthe item to the second buyer, and that does not expose, to the firstbuyer, an identity of the second buyer.
 12. The method of claim 9,wherein the distributed ledger comprises a blockchain.
 13. The method ofclaim 9, wherein the first transfer of resources is different than thesecond transfer of resources.
 14. The method of claim 9, furthercomprising: generate one or more commands directing a user device of thefirst buyer to display a graphical user interface indicating that thereturn has been completed; send, to the user device, the one or morecommands to display the graphical user interface indicating that thereturn has been completed, wherein sending the one or more commands todisplay the graphical user interface indicating that the return has beencompleted causes the user device to display the graphical user interfaceindicating that the return has been completed.
 15. The method of claim9, wherein: the first transfer of resources comprises a fund transferfrom an account of the first buyer to an account of the seller; thesecond transfer of resources comprises a fund transfer from an accountof the second buyer to the account of the seller; and the third transferof resources comprises a fund transfer from the account of the seller tothe account of the first buyer.
 16. The method of claim 9, wherein thefirst buyer is unable to access: the identity of the second buyer usingthe distributed ledger, and an amount paid by the second buyer for theitem.
 17. One or more non-transitory computer-readable media storinginstructions that, when executed by a computing platform for performinga blockchain and smart contract based method to reduce delivery time andprevent reverse supply chain logistics for events corresponding tomultiple accounts while maintaining party anonymity, the computingplatform comprising at least one processor, a communication interface,and memory, cause the computing platform to: receive a first eventprocessing request corresponding to a first sale of an item; process thefirst event processing request, resulting in first event processinginformation indicating a first transfer of resources from a first buyerof the item to a seller of the item; create a first element of adistributed ledger corresponding to the item; record, in the firstelement of the distributed ledger corresponding to the item, the firstevent processing information, an identity of the first buyer, and anidentity of the seller, wherein a first portion of distributed ledger isvisible to the first buyer and the seller, and wherein recording thefirst event processing information further comprises generating a smartcontract indicating when resources are to be transferred from the sellerto the first buyer in case of a return; causing, by communicating with ashipping computing system, the item to be shipped to the first buyer;receive a second event processing request corresponding to a second saleof the item; process the second event processing request, resulting insecond event processing information indicating a second transfer ofresources from a second buyer of the item to the seller; create a secondelement of the distributed ledger corresponding to the item; record, inthe second element of the distributed ledger, the second eventprocessing information, an identity of the second buyer, a return policyfor the item, and the identity of the seller, wherein a second portionof the distributed ledger is visible to the second buyer and the seller,and wherein use of the distributer ledger ensures security of the firstevent processing request and the second event processing request; causethe item to be sent from the first buyer to the second buyer, whereinthe first buyer sent a request to return the item, and wherein causingthe item to be sent from the first buyer to the second buyer comprises:generating, based on the distributed ledger, anonymous shippinginformation corresponding to the second buyer, wherein the anonymousshipping information comprises a quick response (QR) code, allowing thefirst buyer to access the anonymous shipping information using thedistributed ledger, recording shipping confirmation informationindicating that the item has been shipped from the first buyer to thesecond buyer, and recording receipt confirmation information indicatingthat the item has been received by the second buyer, wherein causing theitem to be sent from the first buyer to the second buyer reduces adelivery time associated with shipping the item to the second buyer andprevents the reverse supply chain logistics; identify, using thedistributed ledger, that the item has been received by the second buyer;and based on identifying that the item has been received by the secondbuyer and identifying that conditions of the smart contract have beensatisfied, process a third event, wherein processing the third eventcomprises causes a third transfer of resources, equal to the firsttransfer of resources, from the seller to the first buyer.
 18. The oneor more non-transitory computer-readable media of claim 17, whereingenerating the anonymous shipping information is based on analyzing thereturn policy.
 19. The one or more non-transitory computer-readablemedia of claim 17, wherein the anonymous shipping information furthercomprises a label that may be used by a shipping company to send theitem to the second buyer, and that does not expose, to the first buyer,an identity of the second buyer.
 20. The one or more non-transitorycomputer-readable media of claim 17, wherein the distributed ledgercomprises a blockchain.